[Improve](variant) Keep first duplicate Variant JSON path#63082
Merged
eldenmoon merged 2 commits intoMay 12, 2026
Conversation
Contributor
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
Contributor
There was a problem hiding this comment.
Pull request overview
This PR introduces a backend config to change how VARIANT parsing handles duplicate JSON object keys: when enabled, it keeps the first occurrence instead of erroring on duplicate paths. It also adds test coverage for this behavior, while removing several existing VARIANT nested regression suites and adding a new export/load regression for wide VARIANT data.
Changes:
- Add BE config
variant_enable_duplicate_json_path_check(default off) and implement “keep first duplicate key” behavior during JSON traversal for VARIANT extraction. - Add BE unit tests and a VARIANT regression test + data file to validate duplicate-key behavior (insert + stream load).
- Add an export/load regression test for VARIANT with many potential subcolumns; remove multiple VARIANT nested regression suites.
Reviewed changes
Copilot reviewed 11 out of 12 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
| regression-test/suites/variant_p0/nested2.groovy | Deleted an existing VARIANT nested-type conflict regression suite. |
| regression-test/suites/variant_p0/nested/sql/q01.sql | Deleted SQL outputs for a removed nested VARIANT load suite. |
| regression-test/suites/variant_p0/nested/nested_in_top_array.groovy | Deleted a regression suite covering nested-in-top-array VARIANT behavior. |
| regression-test/suites/variant_p0/nested/load.groovy | Deleted a (mostly commented) nested VARIANT load regression suite. |
| regression-test/suites/variant_p0/nested.groovy | Deleted a large VARIANT nested regression suite. |
| regression-test/suites/variant_p0/duplicate_json_path.groovy | Added regression coverage for keeping the first duplicate JSON key when the new BE config is enabled. |
| regression-test/suites/export_p2/test_export_variant_10k_columns.groovy | Added export→S3→reload regression for wide/sparse VARIANT; currently has correctness and cleanup issues. |
| regression-test/data/variant_p0/duplicate_json_path.json | Added stream-load input with duplicate JSON keys. |
| be/test/storage/segment/variant_util_test.cpp | Added unit tests validating “keep first duplicate key” behavior in both subcolumn-only and doc-mode parsing. |
| be/src/util/json/json_parser.cpp | Added duplicate-key skipping logic during object traversal when the config is enabled. |
| be/src/common/config.h | Declared the new BE config flag. |
| be/src/common/config.cpp | Defined the new BE config flag with default false. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Comment on lines
111
to
132
| if (!config::variant_enable_duplicate_json_path_check) { | ||
| for (auto it = object.begin(); it != object.end(); ++it) { | ||
| const auto& [key, value] = *it; | ||
| traverse_object_member(key, value); | ||
| } | ||
| return; | ||
| } | ||
|
|
||
| std::unordered_set<PathInData, PathInData::Hash> visited_member_paths; | ||
| visited_member_paths.reserve(object.size()); | ||
| for (auto it = object.begin(); it != object.end(); ++it) { | ||
| const auto& [key, value] = *it; | ||
| check_key_length(key); | ||
| ctx.builder.append(key, false); | ||
| PathInData member_path(ctx.builder.get_parts()); | ||
| if (!visited_member_paths.insert(std::move(member_path)).second) { | ||
| ctx.builder.pop_back(); | ||
| continue; | ||
| } | ||
| traverse(value, ctx); | ||
| ctx.builder.pop_back(); | ||
| } |
Comment on lines
+18
to
+22
| suite("duplicate_json_path", "p0") { | ||
| def customBeConfig = [ | ||
| variant_enable_duplicate_json_path_check: true | ||
| ] | ||
| setBeConfigTemporary(customBeConfig) { |
eldenmoon
force-pushed
the
codex/cir-19941-duplicate-json-path
branch
from
a7bc101 to
abc6911
Compare
Member
Author
|
run buildall |
Member
Author
|
/review |
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
I found one additional blocking correctness issue beyond the already-known review threads. The enabled duplicate-path check still allows flat dotted keys and nested object paths to produce the same downstream Variant path string, so the load/WAL failure this PR is meant to prevent can still occur for inputs such as {"a.b":1,"a":{"b":2}}.
Critical checkpoint conclusions:
- Goal/test: The goal is to optionally keep the first duplicate Variant JSON path and avoid duplicate/conflicting subcolumn paths; current tests cover repeated object member names but not dotted-key versus nested-path conflicts, and the implementation does not fully accomplish the goal.
- Scope: The change is small and focused, but the local duplicate key check is too narrow for Variant path identity.
- Concurrency/lifecycle: No new concurrency or special lifecycle management is introduced; the mutable config follows existing BE config patterns.
- Configuration: A disabled-by-default mutable BE config is added; behavior is observed at parse time.
- Compatibility: No storage/protocol format change was found.
- Parallel paths: Existing review thread already covers the JSONB conversion path separately; this comment covers a distinct subcolumn/doc-value path conflict.
- Tests: Added unit/regression coverage misses the dotted-key conflict case; no tests were run by me in this automated review.
- Observability/performance: No additional observability requirement found; the extra check is not on an obviously problematic hot path when disabled.
- User focus: No additional user-provided review focus was supplied.
eldenmoon
force-pushed
the
codex/cir-19941-duplicate-json-path
branch
4 times, most recently
from
961fd01 to
99aa5b6
Compare
Member
Author
|
run buildall |
Member
Author
|
/review |
### What problem does this PR solve?
Issue Number: CIR-19941
Related PR: None
Problem Summary: Variant JSON parsing could emit duplicate or conflicting downstream subcolumn paths when duplicate object keys, flat dotted keys, nested object paths, or array/scalar leaf values normalize to the same Variant path. This could later fail load or WAL replay with subcolumn type size mismatch. Add a disabled-by-default BE config to enable duplicate JSON path checking; when enabled, duplicate leaf paths keep the first value while object entries that expand to distinct child paths are preserved. The duplicate-check setting is captured in ParseConfig so parser and materialization use the same per-call behavior.
### Release note
Add BE config variant_enable_duplicate_json_path_check to keep the first duplicate Variant JSON leaf path when enabled; default is false.
### Check List (For Author)
- Test: Unit Test and Regression test
- Unit Test: ./run-be-ut.sh --run --filter='VariantUtilTest.ParseDuplicateJsonPaths*'
- Build: source ./custom_env.sh; export DORIS_PARALLELISM="${DORIS_PARALLELISM:-39}"; export BUILD_TYPE="${BUILD_TYPE:-ASAN}"; export USE_MEM_TRACKER=ON; ./build.sh --be -j"${DORIS_PARALLELISM}"
- Regression test: env -u http_proxy -u https_proxy -u HTTP_PROXY -u HTTPS_PROXY -u all_proxy -u ALL_PROXY NO_PROXY=127.0.0.1,localhost,172.19.0.1 no_proxy=127.0.0.1,localhost,172.19.0.1 ./run-regression-test.sh --run --conf tmp/regression-conf.auto.groovy -d variant_p0 -s duplicate_json_path
- Review: GPT-5.5 xhigh subagent final review found no P0/P1 blocking issues
- Behavior changed: Yes. When variant_enable_duplicate_json_path_check is enabled, duplicate downstream leaf paths keep the first value and duplicate object entries can merge distinct child paths; default is false.
- Does this need documentation: No
eldenmoon
force-pushed
the
codex/cir-19941-duplicate-json-path
branch
from
99aa5b6 to
102aad0
Compare
Contributor
There was a problem hiding this comment.
Review conclusion: request changes. I did not add duplicate inline comments because the remaining blocking concern is already covered by an existing thread on be/src/util/json/json_parser.cpp: traverseObjectAsJsonb() still preserves duplicate object keys inside JSONB output when variant_enable_duplicate_json_path_check is enabled, so nested arrays/objects converted through the JSONB path do not consistently keep the first duplicate key.
Critical checkpoints:
- Goal/test: The PR aims to make duplicate Variant JSON paths keep the first value when enabled. The added BE unit and regression tests cover subcolumn/doc materialization, flat dotted keys, object/scalar conflicts, insert, stream load, and compaction, but the JSONB conversion path remains uncovered and inconsistent with the config comment.
- Scope/focus: The code is mostly focused on Variant parsing and materialization; no unrelated current PR file changes were found in the GitHub PR diff.
- Concurrency/lifecycle: No new concurrent state or non-trivial lifecycle management is introduced. The new mutable config is read per parse/materialization call into
ParseConfig; no lock-order or thread lifecycle issue was found. - Configuration: A mutable BE config is added and propagated to the main deserialize/materialize paths, but behavior is not applied uniformly to JSONB serialization of nested arrays/objects.
- Compatibility/storage: No serialized format or FE/BE protocol format change was found. Default behavior remains disabled, so compatibility risk is limited.
- Parallel paths: The subcolumn/doc-value path is updated, but the JSONB path remains a parallel path with inconsistent duplicate handling.
- Tests/results: Tests are meaningful for the updated paths and use ordered query output. Missing coverage remains for JSONB duplicate-key handling under the new config.
- Observability/performance: No extra observability appears necessary. The duplicate path checks add per-row hash-set work only when enabled; no additional performance blocker found.
User focus: no additional user-provided review focus was specified.
Existing review context: The earlier flat-dot/nested path-collision concern appears addressed in the current head by parser-level get_path() deduplication plus path normalization/materialization tests. The earlier regression-test deletion concern appears stale for the current GitHub PR file list. The JSONB duplicate-key concern remains applicable and should be resolved before approval.
Member
Author
|
run buildall |
Contributor
TPC-H: Total hot run time: 29950 ms |
Contributor
TPC-DS: Total hot run time: 170427 ms |
Contributor
BE UT Coverage ReportIncrement line coverage Increment coverage report
|
eldenmoon
changed the title
csun5285
reviewed
May 11, 2026
| const auto& path_name = path.get_path(); | ||
| for (auto& entry : column_variant.get_subcolumns()) { | ||
| if (entry->path.get_path() == path_name && is_plain_path(entry->path)) { | ||
| subcolumn = &entry->data; |
Contributor
There was a problem hiding this comment.
如果 check_duplicate_json_path 是true 的时候，path 都是normalized_plain_path, 这个分支 这个不可能走到。
| void traverse(const Element& element, ParseContext& ctx); | ||
| void traverseObject(const JSONObject& object, ParseContext& ctx); | ||
| void traverseArray(const JSONArray& array, ParseContext& ctx); | ||
| bool tryAppendValue(ParseContext& ctx, const PathInData::Parts& path, Field&& value, |
Contributor
There was a problem hiding this comment.
这个函数的返回值似乎没被用到过，如果tryAppendValue 失败会怎么样
| @@ -0,0 +1,7 @@ | |||
| {"k":8,"v":{"a":42,"a":{"b":42}}} | |||
| {"k":9,"v":{"a":123,"a":"123"}} | |||
Contributor
There was a problem hiding this comment.
这个设置 variant_enable_duplicate_json_path_check 是true 了，还是有两个 a ，这个变量variant_enable_duplicate_json_path_check为true ，期望报错还是默认丢弃一个还是其他。
### What problem does this PR solve? Issue Number: CIR-19941 Related PR: apache#63082 Problem Summary: Address review comments around duplicate Variant JSON path handling. The parser helper now has no unused return value and clearly skips duplicate paths to keep the first value. The materialization path no longer carries an unreachable duplicate-path fallback after path normalization, and the regression test documents the keep-first expectation for duplicate keys. ### Release note None ### Check List (For Author) - Test: Unit Test - Unit Test: ./run-be-ut.sh --run --filter=VariantUtilTest.* - Format: /mnt/disk1/claude-max/ldb_toolchain16/bin/clang-format-16 -i be/src/util/json/json_parser.h be/src/util/json/json_parser.cpp be/src/exec/common/variant_util.cpp - Behavior changed: No - Does this need documentation: No
Member
Author
|
run buildall |
Contributor
TPC-H: Total hot run time: 29703 ms |
Contributor
TPC-DS: Total hot run time: 172174 ms |
Contributor
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
Member
Author
|
/review |
Contributor
There was a problem hiding this comment.
I found one blocking correctness issue in the new duplicate path handling. The PR goal is clear and mostly focused, and it adds both BE unit coverage and a regression case for duplicate object keys, flat/nested path conflicts, doc mode, stream load, and compaction. However, array aggregation still has a distinct flat-key/nested-path collision path that can silently drop values when the duplicate check is enabled.
Critical checkpoint conclusions:
- Goal/test: The PR aims to keep the first duplicate Variant JSON path when enabled; current tests cover object-level duplicates but miss duplicate logical paths produced by different elements of the same array.
- Scope: The implementation is small and focused, but the array path handling needs to be included for correctness.
- Concurrency/lifecycle: No new shared mutable lifecycle or locking concerns beyond reading the mutable BE config per parse.
- Configuration: The new BE config is mutable and is read at parse/materialization entry points; behavior remains disabled by default.
- Compatibility: No storage-format or thrift incompatibility found.
- Parallel paths: Subcolumn and doc-value paths are both wired, but the array aggregation path remains inconsistent.
- Tests: Existing new tests are useful but need an array case like {"x":[{"a.b":1},{"a":{"b":2}}]} to prove values are merged rather than dropped.
- Observability/performance/transactions: No additional observability, transaction, or obvious performance concerns found for this focused change.
User focus: No additional user-provided review focus was supplied.
csun5285
approved these changes
May 11, 2026
yiguolei
approved these changes
May 12, 2026
Contributor
|
PR approved by at least one committer and no changes requested. |
github-actions
Bot
added
the
approved
github-actions Bot
pushed a commit
that referenced
this pull request
May 12, 2026
Add BE config variant_enable_duplicate_json_path_check to keep the first duplicate JSON object key during Variant parsing when enabled.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add BE config variant_enable_duplicate_json_path_check to keep the first duplicate JSON object key during Variant parsing when enabled.